collection

  • collection
  • Min-IOP (Minimum Interoperable Subset) Use Cases
  • 2.  Use Cases
  • 2.4.  Scheduling

2.4.4. Recurrence

Similar to basic recurrence, changes to unbounded, repeating meetings/events should retain their unboundedness when a change is made to one or all instances of the meeting/event.

  • 2.4.4.1.  Change all instances
  • 2.4.4.2.  Change one instance
  • 2.4.4.3.  Extending a series
  • 2.4.4.4.  Adding an extra date that is an exception to a series
  • 2.4.4.5.  Change the body of all instances
  • 2.4.4.6.  Change the body of one instance
  • 2.4.4.7.  Add/Remove attendee to/from all instances
  • 2.4.4.8.  Add/Remove attendee to/from one instance
  • 2.4.4.9.  This and future